Skip to content

Conversation

@nikic
Copy link
Contributor

@nikic nikic commented Jan 6, 2026

@rustbot
Copy link
Collaborator

rustbot commented Jan 6, 2026

These commits modify compiler targets.
(See the Target Tier Policy.)

@rustbot rustbot added A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 6, 2026
@rustbot
Copy link
Collaborator

rustbot commented Jan 6, 2026

⚠️ Warning ⚠️

@nikic
Copy link
Contributor Author

nikic commented Jan 6, 2026

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Jan 6, 2026
@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Jan 6, 2026
@rust-log-analyzer

This comment has been minimized.

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 6, 2026

☀️ Try build successful (CI)
Build commit: dabe9cd (dabe9cd2e5a1630ac5ed5f1b87f891b6dc563025, parent: da476f1942868cdf94ed88b01ea31170cfe95047)

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (dabe9cd): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

Benchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @rustbot label: +perf-regression-triaged. If not, please fix the regressions and do another perf run. If its results are neutral or positive, the label will be automatically removed.

@bors rollup=never
@rustbot label: -S-waiting-on-perf +perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
0.9% [0.2%, 8.9%] 228
Regressions ❌
(secondary)
1.4% [0.2%, 8.0%] 260
Improvements ✅
(primary)
-0.8% [-1.1%, -0.3%] 6
Improvements ✅
(secondary)
-2.2% [-8.0%, -0.2%] 28
All ❌✅ (primary) 0.9% [-1.1%, 8.9%] 234

Max RSS (memory usage)

Results (primary 1.0%, secondary -1.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
1.0% [0.8%, 1.3%] 2
Regressions ❌
(secondary)
1.8% [0.9%, 2.4%] 8
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.7% [-4.8%, -2.6%] 10
All ❌✅ (primary) 1.0% [0.8%, 1.3%] 2

Cycles

Results (primary 3.2%, secondary 2.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
3.2% [1.6%, 10.2%] 19
Regressions ❌
(secondary)
3.3% [1.3%, 7.4%] 38
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-4.8% [-7.5%, -2.5%] 7
All ❌✅ (primary) 3.2% [1.6%, 10.2%] 19

Binary size

Results (primary -0.6%, secondary -1.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
0.1% [0.1%, 0.1%] 4
Regressions ❌
(secondary)
2.6% [0.1%, 5.1%] 2
Improvements ✅
(primary)
-0.8% [-1.5%, -0.1%] 14
Improvements ✅
(secondary)
-1.1% [-3.9%, -0.0%] 93
All ❌✅ (primary) -0.6% [-1.5%, 0.1%] 18

Bootstrap: 473.133s -> 480.877s (1.64%)
Artifact size: 390.77 MiB -> 402.18 MiB (2.92%)

@rust-bors

This comment was marked as outdated.

@rustbot rustbot added perf-regression Performance regression. and removed S-waiting-on-perf Status: Waiting on a perf run to be completed. labels Jan 6, 2026
@rust-timer

This comment was marked as outdated.

@rust-log-analyzer

This comment has been minimized.

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 6, 2026

☔ The latest upstream changes made this pull request unmergeable. Please resolve the merge conflicts.

@bors
Copy link
Collaborator

bors commented Jan 6, 2026

☔ The latest upstream changes (presumably #150726) made this pull request unmergeable. Please resolve the merge conflicts.

@nikic
Copy link
Contributor Author

nikic commented Jan 8, 2026

Based on helloworld, the perf regressions seem to be related to the allocator somehow. Previously tcache_alloc_small_hard was called 3 times, now it's called 189 times. The total number of allocations is smaller, but the time spent in the allocator is larger.

@nikic
Copy link
Contributor Author

nikic commented Jan 8, 2026

Or maybe the issue is not actually the allocator behavior itself. I suspect that we might have lost LTO on jemalloc and tcache_alloc_small_hard previously got inlined into malloc_default but now no longer is. Possibly updating the host toolchain at the same time so that the versions match will help.

@rustbot rustbot added A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Jan 8, 2026
@rustbot

This comment has been minimized.

@nikic
Copy link
Contributor Author

nikic commented Jan 27, 2026

r? @cuviper

@cuviper
Copy link
Member

cuviper commented Jan 27, 2026

@bors r+ rollup=never

@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 27, 2026

📌 Commit e015fc8 has been approved by cuviper

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Jan 27, 2026
@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Jan 27, 2026
Update to LLVM 22

Scheduled release date: Feb 24
1.94 becomes stable: Mar 5

Changes:
 * Update to rc2, with one patch to work around our outdated illumos sysroot (rust-lang/llvm-project@41256ab).
 * Update the host toolchain as well, otherwise we lose cross-language LTO, in particular for jemalloc.
 * Adjust one loongarch assembly test. The split into r and s variants is based on the suggestion in #151134.

Depends on:

 * [x] #151410
 * [ ] #150756
 * [x] llvm/llvm-project#175190
 * [x] llvm/llvm-project#175912
 * [x] llvm/llvm-project#175965
 * [x] llvm/llvm-project#176195
 * [x] llvm/llvm-project#157073
 * [x] llvm/llvm-project#176421
 * [x] llvm/llvm-project#176925
 * [x] llvm/llvm-project#177187
@rust-bors rust-bors bot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jan 28, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 28, 2026

💔 Test for 917820a failed: CI

@ZuseZ4
Copy link
Member

ZuseZ4 commented Jan 28, 2026

@bors retry

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 28, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jan 28, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Jan 28, 2026

☀️ Test successful - CI
Approved by: cuviper
Duration: 3h 19m 37s
Pushing 466ea4e to main...

@rust-bors rust-bors bot merged commit 466ea4e into rust-lang:main Jan 28, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Jan 28, 2026
@github-actions
Copy link
Contributor

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing e96bb7e (parent) -> 466ea4e (this PR)

Test differences

Show 51 test diffs

Stage 1

  • [codegen] tests/codegen-llvm/amdgpu-addrspacecast.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/amdgpu-addrspacecast.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/deduced-param-attrs.rs#LLVM20: ignore (ignored when the LLVM version (21.1.8) is newer than majorversion 20) -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 20) (J4)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: ignore (ignored when the LLVM version (21.1.8) is newer than majorversion 20) -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 20) (J4)
  • [codegen] tests/codegen-llvm/issues/issue-122600-ptr-discriminant-update.rs#new: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/issues/issue-122600-ptr-discriminant-update.rs#old: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-gather.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-gather.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-load.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-load.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-store.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-store.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-scatter.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-scatter.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/vec_pop_push_noop.rs#new: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/vec_pop_push_noop.rs#old: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [codegen] tests/codegen-llvm/vecdeque_pop_push.rs#new: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J4)
  • [codegen] tests/codegen-llvm/vecdeque_pop_push.rs#old: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J4)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32r: [missing] -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J5)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32r: [missing] -> ignore (ignored when the LLVM version 20.1.2 is older than 22.0.0) (J7)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32: pass -> [missing] (J8)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32s: [missing] -> pass (J8)

Stage 2

  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32r: [missing] -> pass (J0)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM20: ignore (ignored when the LLVM version (21.1.8) is newer than majorversion 20) -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 20) (J0)
  • [codegen] tests/codegen-llvm/amdgpu-addrspacecast.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/amdgpu-addrspacecast.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/deduced-param-attrs.rs#LLVM20: ignore (ignored when the LLVM version (21.1.8) is newer than majorversion 20) -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 20) (J0)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: ignore (ignored when the LLVM version (21.1.8) is newer than majorversion 20) -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 20) (J0)
  • [codegen] tests/codegen-llvm/issues/issue-122600-ptr-discriminant-update.rs#new: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/issues/issue-122600-ptr-discriminant-update.rs#old: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-gather.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-gather.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-load.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-load.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-store.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-masked-store.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-scatter.rs#LLVM21: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/simd-intrinsic/simd-intrinsic-generic-scatter.rs#LLVM22: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/vec_pop_push_noop.rs#new: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/vec_pop_push_noop.rs#old: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [codegen] tests/codegen-llvm/vecdeque_pop_push.rs#new: ignore (ignored when the LLVM version 21.1.8 is older than 22.0.0) -> pass (J0)
  • [codegen] tests/codegen-llvm/vecdeque_pop_push.rs#old: pass -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 21) (J0)
  • [run-make] tests/run-make/compressed-debuginfo-zstd: pass -> ignore (ignored if LLVM wasn't build with zstd for ELF section compression or LLVM is not the default codegen backend) (J1)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32: pass -> [missing] (J2)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32s: [missing] -> pass (J2)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32r: [missing] -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J3)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32r: [missing] -> ignore (ignored when the LLVM version 20.1.8 is older than 22.0.0) (J6)
  • [assembly] tests/assembly-llvm/asm/loongarch-type.rs#loongarch32r: [missing] -> ignore (ignored when the LLVM version 20.1.2 is older than 22.0.0) (J9)
  • [ui] tests/ui/sanitizer/kcfi-arity-requires-llvm-21-0-0.rs: ignore (ignored when the LLVM version (21.1.8) is newer than majorversion 20) -> ignore (ignored when the LLVM version (22.1.0) is newer than majorversion 20) (J10)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 466ea4e6c39f8a43727edcc726ca86b499e14d83 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. pr-check-1: 1701.6s -> 2757.3s (+62.0%)
  2. x86_64-rust-for-linux: 2608.5s -> 4155.2s (+59.3%)
  3. pr-check-2: 2299.3s -> 3415.9s (+48.6%)
  4. x86_64-gnu-tools: 3478.0s -> 4931.2s (+41.8%)
  5. x86_64-gnu-gcc: 3784.3s -> 5209.1s (+37.7%)
  6. x86_64-gnu-miri: 4414.5s -> 5948.0s (+34.7%)
  7. armhf-gnu: 4940.1s -> 6630.2s (+34.2%)
  8. test-various: 7021.9s -> 8888.0s (+26.6%)
  9. dist-arm-linux-musl: 5613.5s -> 6918.5s (+23.2%)
  10. arm-android: 5871.7s -> 7207.8s (+22.8%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (466ea4e): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
3.2% [0.9%, 7.4%] 3
Regressions ❌
(secondary)
2.3% [0.4%, 6.0%] 3
Improvements ✅
(primary)
-0.7% [-2.8%, -0.2%] 238
Improvements ✅
(secondary)
-0.9% [-10.1%, -0.1%] 299
All ❌✅ (primary) -0.6% [-2.8%, 7.4%] 241

Max RSS (memory usage)

Results (primary 0.7%, secondary -1.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
2.9% [1.4%, 5.4%] 3
Regressions ❌
(secondary)
1.9% [0.6%, 3.2%] 6
Improvements ✅
(primary)
-2.7% [-4.0%, -1.3%] 2
Improvements ✅
(secondary)
-3.2% [-5.0%, -0.6%] 10
All ❌✅ (primary) 0.7% [-4.0%, 5.4%] 5

Cycles

Results (primary 2.8%, secondary 1.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
3.7% [2.0%, 8.5%] 6
Regressions ❌
(secondary)
3.9% [2.1%, 7.2%] 10
Improvements ✅
(primary)
-3.0% [-3.0%, -3.0%] 1
Improvements ✅
(secondary)
-4.7% [-7.0%, -2.0%] 4
All ❌✅ (primary) 2.8% [-3.0%, 8.5%] 7

Binary size

Results (primary -0.3%, secondary -1.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
0.1% [0.1%, 0.1%] 4
Regressions ❌
(secondary)
2.6% [0.1%, 5.1%] 2
Improvements ✅
(primary)
-0.4% [-1.4%, -0.1%] 49
Improvements ✅
(secondary)
-1.1% [-3.8%, -0.0%] 97
All ❌✅ (primary) -0.3% [-1.4%, 0.1%] 53

Bootstrap: 470.891s -> 476.499s (1.19%)
Artifact size: 383.44 MiB -> 397.91 MiB (3.77%)

@petrochenkov
Copy link
Contributor

Looks like this is causing some segfaults in LoopDeletionPass - #151790.

@nnethercote
Copy link
Contributor

About the perf results: the icount results look great, but LLVM updates are big enough that looking at the cycle counts and wall-times is reasonable -- more so than typical PRs that make very small changes. In this case the cycle count and wall-time results are a little bit in the red. We saw a similar thing with the LLVM 21 update. This is different to the previous few LLVM updates before 21 where we saw uniform improvements across icounts/cycles/wall-time.

I'm not sure what to make of this, and it's not going to stop us from updating to LLVM 22. But it seems worth mentioning.

@@ -5,7 +5,7 @@ set -ex
source shared.sh

# Try to keep the LLVM version here in sync with src/ci/scripts/install-clang.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this comment be updated? That script is on LLVM 20 and the update cadence seems to be intentionally different.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should drop this comment, people are regularly confused by it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well we should still try to keep those two close :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.